Transaction layer packet formatting

ABSTRACT

A method and apparatus for enhancing/extending a serial point-to-point interconnect architecture, such as Peripheral Component Interconnect Express (PCIe) is herein described. Temporal and locality caching hints and prefetching hints are provided to improve system wide caching and prefetching. Message codes for atomic operations to arbitrate ownership between system devices/resources are included to allow efficient access/ownership of shared data. Loose transaction ordering provided for while maintaining corresponding transaction priority to memory locations to ensure data integrity and efficient memory access. Active power sub-states and setting thereof is included to allow for more efficient power management. And, caching of device local memory in a host address space, as well as caching of system memory in a device local memory address space is provided for to improve bandwidth and latency for memory accesses.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a continuation (and claims the benefit of priorityunder 35 U.S.C. §120) of U.S. application Ser. No. 13/713,635, filed onDec. 13, 2012, now issued as U.S. Pat. No. 9,026,682, and entitled PCIEXPRESS ENHANCEMENTS AND EXTENSIONS, which application is a continuationof U.S. patent application Ser. No. 12/883,781, filed on Sep. 16, 2010,now issued as U.S. Pat. No. 8,549,183, which application is acontinuation of U.S. patent application Ser. No. 11/592,341, filed onNov. 2, 2006, now issued as U.S. Pat. No. 7,949,794. The disclosures ofthe prior Applications are considered part of and is incorporated byreference in the disclosure of this Application.

FIELD

This invention relates to the field of interconnects and, in particular,to extensions for serial point-to-point interconnects.

BACKGROUND

Computer systems include a number of components and elements. Often thecomponents are coupled via a bus or interconnect. Previously,input/output (I/O) devices were coupled together through a conventionalmulti-drop parallel bus architecture referred to as Peripheral ComponentInterconnect (PCI). More recently, a new generation of an I/O busreferred to as PCI-Express (PCIe) has been used to facilitate fasterinterconnection between devices utilizing a serial physical-layercommunication protocol.

A PCIE architecture includes a layered protocol to communicate betweendevice. As an example, a physical layer, link layer, and transactionlayer form a PCIE protocol stack. The PCIe link is built arounddedicated unidirectional pairs of serial point-to-point connectionsreferred to as a lane. A link between devices includes some number oflanes, such as one, two, sixteen, thirty-two, and so-on. The currentPCIE specification, base spec 1.1, is available athttp://www.pcisig.com/specifications/pciexpress/.

Currently, PCIe links maintain coherency with respect to processorcaches and system memory. For example, a read/write to an I/O devicemisses a cache, retrieves a referenced element, performs a requestedoperation, and then immediately evicts the element from the cache. Inother words, an I/O write is checked against a processor cache, but theI/O access is not cache coherent. Furthermore, uncacheable MMIO accessesare uncacheable and are also not coherent. Therefore, I/O accesses areexpensive for system operation and potentially decrease processingbandwidth.

In addition, when an I/O device operates on shared memory, the devicetypically acquires a system wide lock, performs operations on the sharedmemory, and then releases the lock. Acquiring a lock in this mannerpotentially results in data serialization and expensive delays inassociation with operating on shared data with multiple processingelements. Often microprocessors provide mechanisms for multiple threadsto perform atomic operations to avoid the penalty associated with locks.Yet, currently PCIe does not provide a direct ability to atomicallyoperate on shared data.

Moreover, devices issue transactions in any order, which, in someinstances, results in inefficient memory accesses, such as thrashing ofpages of memory. For example, a first transaction is issued referencinga first location in a first page of memory, a second transactionreferencing a second location in a second page of memory, and a thirdtransaction referencing a third location in the first page of memory.Here, the first page is opened to service the first transaction, thefirst page is closed, the second page is opened to service the secondtransaction, the second page is closed, and then the first page has tobe re-opened to service the third transaction.

As devices/components become more complex and undertake heavierworkloads, power management also becomes an increasing concern.Previously, PCIe compliant devices are capable of entering a pluralityof power states. However, the power states include a single active stateand a plurality of different levels of an “off” state, i.e. the deviceconsumes different levels of power but is potentially not operable.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not intendedto be limited by the figures of the accompanying drawings.

FIG. 1 illustrates an embodiment of a system including a serialpoint-to-point interconnect to connect I/O devices in a computer system.

FIG. 2 illustrates an embodiment of a layered protocol stack.

FIG. 3 illustrates an embodiment of a transaction descriptor.

FIG. 4 illustrates an embodiment of a serial point-to-point link.

FIG. 5 illustrates an embodiment of a system including a device coupledto a controller hub through a serial point-to-point link capable oftransmitting/receiving cache/prefetch hints.

FIG. 6 illustrates an embodiment of a list of device request accesssemantics.

FIG. 7 illustrates an embodiment of a list of access control hints(ACH).

FIG. 8 illustrates an embodiment of a packet including an ACH field.

FIG. 9 illustrates an embodiment of a prefetch message.

FIG. 10 illustrates an embodiment of a heading including an ACH fieldand a prefetch hint.

FIG. 11 illustrates an embodiment of a flow diagram for a method ofproviding access control and/or prefetch hints.

FIG. 12 illustrates an embodiment of a system capable of performingatomic operations on shared data.

FIG. 13 illustrates an embodiment of a packet including a field tospecify an atomic operation.

FIG. 14 illustrates an embodiment of an atomic operation responsepacket.

FIG. 15 illustrates an embodiment of a flow diagram for performing anatomic operation.

FIG. 16 illustrates an embodiment of a system capable of re-orderingissued transactions for efficient memory access.

FIG. 17 illustrates an embodiment of a flow diagram for re-orderingtransactions.

FIG. 18 illustrates an embodiment of a storage element to set a powerstate and a table to associate power states with power and performancemetrics.

FIG. 19 illustrates an embodiment of a flow diagram for a method ofsetting active sub-state in a device.

FIG. 20 illustrates an embodiment of a system including a portion oflocal memory mapped into a host memory space and a portion of systemmemory mapped into a local memory space.

FIG. 21 illustrates an embodiment of a system including an I/O devicehaving a cache.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forthsuch as examples of specific interconnects, specific packets/messages,specific fields and locations within packets/messages, specific locationof logic/caches, specific caching/prefetch hints, specificpower/performance metrics, etc. in order to provide a thoroughunderstanding of the present invention. It will be apparent, however, toone skilled in the art that these specific details need not be employedto practice the present invention. In other instances, well knowncomponents or methods, such as cache logic/implementation, peripheralComponent Interconnect Express (PCIe) messaging protocols, PCIefields/packets in transactions, and other PCIe basic implementation havenot been described in detail in order to avoid unnecessarily obscuringthe present invention.

The method and apparatus described herein are for extending/enhancingserial point-to-point interconnect architecture. Specifically,interconnect enhancement is primarily discussed in reference to agraphic accelerator coupled to a controller hub/root controller throughPCIe link. However, the methods and apparatus for extending a serialpoint-to-point link are not so limited, as they may be implemented on orin association with any integrated circuit device, such as anyinput/output device or other computer component, as well as inconjunction with any type of serial point-to-point interconnect.

Serial Point-to-Point Layered Protocol Link/Interconnect

Referring to FIG. 1, an embodiment of a system including devices coupledto a controller hub via a serial link is illustrated. System 100includes processor 105 and system memory 110 coupled to controller hub115. Processor 105 includes any processing element, such as amicroprocessor, a host processor, an embedded processor, a co-processor,or other processor. Processor 105 is coupled to controller hub 115through front-side bus (FSB) 106. In one embodiment, FSB 106 is a serialpoint-to-point interconnect as described below.

System memory 110 includes any memory device, such as random accessmemory (RAM), non-volatile (NV) memory, or other memory accessible bydevices in system 100. System memory 110 is coupled to controller hub115 through memory interface 116. Examples of a memory interface includea double-data rate (DDR) memory interface, a dual-channel DDR memoryinterface, and a dynamic RAM (DRAM) memory interface.

In one embodiment, controller hub 115 is a root hub or root controllerin a Peripheral Component Interconnect Express (PCIe or PCIE)interconnection hierarchy. Examples of controller hub 115 include achipset, a memory controller hub (MCH), a northbridge, an interconnectcontroller hub (ICH) a southbridge, and a root controller/hub. Often theterm chipset refers to two physically separate controller hubs, i.e. amemory controller hub (MCH) coupled to an interconnect controller hub(ICH).

Here, controller hub 115 is coupled to switch/bridge 120 through seriallink 119. Input/output modules 117 and 121, which may also be referredto as interfaces/ports 117 and 121, include/implement a layered protocolstack to provide communication between controller hub 115 and switch120. A module, such as modules 117, 118, 121, 122, 126, and 131, may beimplemented in hardware, software, firmware, or any combination thereof.Furthermore, module boundaries commonly vary and functions areimplemented together, as well as separately in different embodiments. Inone embodiment, multiple devices are capable of being coupled to switch120.

Switch 120 routes packets/messages from device 125 upstream, i.e. up ahierarchy towards a root controller, to controller hub 115 anddownstream, i.e. down a hierarchy away from a root controller, fromprocessor 105 or system memory 110 to device 125. Device 125 includesany internal or external device or component to be coupled to anelectronic system, such as an I/O device, a Network Interface Controller(NIC), an add-in card, an audio processor, a network processor, ahard-drive, a storage device, a CD/DVD ROM, a monitor, a printer, amouse, a keyboard, a router, a portable storage device, a Firewiredevice, a Universal Serial Bus (USB) device, a scanner, and otherinput/output devices.

Graphics accelerator 130 is also coupled to controller hub 115 throughserial link 132. In one embodiment, graphics accelerator 130 is coupledto an MCH, which is coupled to an ICH. Switch 120, and accordingly I/Odevice 125, is then coupled to the ICH. I/O modules 131 and 118 are alsoto implement a layered protocol stack to communicate between graphicsaccelerator 130 and controller hub 115.

Turning to FIG. 2 an embodiment of a layered protocol stack isillustrated. Layered protocol stack 200 includes any layeredcommunication stack, such as a common standard interface (CSI) stack,PCIe stack, or other protocol stack. In one embodiment, protocol stack200 is a PCIe protocol stack including transaction layer 205, link layer210, and physical layer 220. An interface, such as interfaces 117, 118,121, 122, 126, and 131 in FIG. 1, may be represented as communicationprotocol stack 200. Representation as a communication protocol stack isalso referred to as a module or interface implementing/including aprotocol stack.

Transaction Layer

In one embodiment, transaction layer 205 is to provide an interfacebetween a device's processing core and the interconnect architecture,such as data link layer 210 and physical layer 220. In this regard, aprimary responsibility of the transaction layer 205 is the assembly anddisassembly of packets (i.e., transaction layer packets, or TLPs). PCIeimplements split transactions, i.e. transactions with request andresponse separated by time, allowing a link to carry other traffic whilethe target device gathers data for the response.

In addition PCIe utilizes credit-based flow control. In this scheme, adevice advertises an initial amount of credit for each of the receivebuffers in Transaction Layer 205. An external device at the opposite endof the link, such as controller hub 115 in FIG. 1, counts the number ofcredits consumed by each TLP. A transaction may be transmitted if thetransaction does not exceed a credit limit. Upon receiving a response anamount of credit is restored. An advantage of a credit scheme is thatthe latency of credit return does not affect performance, provided thatthe credit limit is not encountered.

In one embodiment, four transaction address spaces include aconfiguration address space, a memory address space, an input/outputaddress space, and a message address space. Memory space transactionsinclude one or more of read requests and write requests to transfer datato/from a memory-mapped location. In one embodiment, memory spacetransactions are capable of using two different address formats, e.g., ashort address format, such as a 32-bit address, or a long addressformat, such as 64-bit address. Configuration space transactions areused to access configuration space of the PCIe devices. Transactions tothe configuration space include read requests and write requests.Message space transactions (or, simply messages) are defined to supportin-band communication between PCIe agents.

Therefore, in one embodiment, transaction layer 205 assembles packetheader/payload 206. Format for packet headers/payloads may be found inthe PCIe specification, i.e. the PCIe base spec 1.1, which is availableat http://www.pcisig.com/specifications/pciexpress/.

Quickly referring to FIG. 3, an embodiment of a PCIe transactiondescriptor is illustrated. In one embodiment, transaction descriptor 300is a mechanism for carrying transaction information. In this regard,transaction descriptor 300 supports identification of transactions in asystem. Other potential uses include tracking modifications of defaulttransaction ordering and association of transaction with channels.

Transaction descriptor 300 includes global identifier field 302,attributes field 304 and channel identifier field 306. In theillustrated example, global identifier field 302 is depicted comprisinglocal transaction identifier field 308 and source identifier field 310.In one embodiment, global transaction identifier 302 is unique for alloutstanding requests.

According to one implementation, local transaction identifier field 308is a field generated by a requesting agent, and it is unique for alloutstanding requests that require a completion for that requestingagent. Furthermore, in this example, source identifier 310 uniquelyidentifies the requestor agent within a PCIe hierarchy. Accordingly,together with source ID 310, local transaction identifier 308 fieldprovides global identification of a transaction within a hierarchydomain.

Attributes field 304 specifies characteristics and relationships of thetransaction. In this regard, attributes field 304 is potentially used toprovide additional information that allows modification of the defaulthandling of transactions. In one embodiment, attributes field 304includes priority field 312, reserved field 314, ordering field 316, andno-snoop field 318. Here, priority sub-field 312 may be modified by aninitiator to assign a priority to the transaction. Reserved attributefield 314 is left reserved for future, or vendor-defined usage. Possibleusage models using priority or security attributes may be implementedusing the reserved attribute field.

In this example, ordering attribute field 316 is used to supply optionalinformation conveying the type of ordering that may modify defaultordering rules. According to one example implementation, an orderingattribute of “0” denotes default ordering rules are to apply, wherein anordering attribute of “1” denotes relaxed ordering, wherein writes canpass writes in the same direction, and read completions can pass writesin the same direction. Snoop attribute field 318 is utilized todetermine if transactions are snooped. As shown, channel ID Field 306identifies a channel that a transaction is associated with.

Link Layer

Link layer 210, also referred to as data link layer 210, acts as anintermediate stage between transaction layer 205 and the physical layer220. In one embodiment, a responsibility of the data link layer 210 isproviding a reliable mechanism for exchanging Transaction Layer Packets(TLPs) between two components a link. One side of the Data Link Layer210 accepts TLPs assembled by the Transaction Layer 205, applies packetsequence identifier 211, i.e. an identification number or packet number,calculates and applies an error detection code, i.e. CRC 212, andsubmits the modified TLPs to the Physical Layer 220 for transmissionacross a physical to an external device.

Physical Layer

In one embodiment, physical layer 220 includes logical sub block 221 andelectrical sub-block 222 to physically transmit a packet to an externaldevice. Here, logical sub-block 221 is responsible for the “digital”functions of Physical Layer 221. In this regard, the logical sub-blockincludes a transmit section to prepare outgoing information fortransmission by physical sub-block 222, and a receiver section toidentify and prepare received information before passing it to the LinkLayer 210.

Physical block 222 includes a transmitter and a receiver. Thetransmitter is supplied by logical sub-block 221 with symbols, which thetransmitter serializes and transmits onto to an external device. Thereceiver is supplied with serialized symbols from an external device andtransforms the received signals into a bit-stream. The bit-stream isde-serialized and supplied to logical sub-block 221. In one embodiment,an 8b/10b transmission code is employed, where ten-bit symbols aretransmitted/received. Here, special symbols are used to frame a packetwith frames 223. In addition, in one example, the receiver also providesa symbol clock recovered from the incoming serial stream.

As stated above, although transaction layer 205, link layer 210, andphysical layer 220 are discussed in reference to a specific embodimentof a PCIe protocol stack, a layered protocol stack is not so limited. Infact, any layered protocol may be included/implemented. As an example,an port/interface that is represented as a layered protocol includes:(1) a first layer to assemble packets, i.e. a transaction layer; asecond layer to sequence packets, i.e. a link layer; and a third layerto transmit the packets, i.e. a physical layer. As a specific example, acommon standard interface (CSI) layered protocol is utilized.

Referring next to FIG. 4 an embodiment of a PCIe serial point to pointlink is illustrated. Although an embodiment of a PCIe serialpoint-to-point link is illustrated, a serial point-to-point link is notso limited, as it includes any transmission path for transmitting serialdata. In the embodiment shown, at an electrical level, twounidirectional differential pairs form a lane. Accordingly, device 405includes transmission logic 406 to transmit data to device 410 andreceiving logic 407 to receive data from device 410. In other words, twotransmitting paths, i.e. paths 416 and 417, and two receiving paths,i.e. paths 418 and 419, are included in a PCIe lane.

A transmission path refers to any path for transmitting data, such as atransmission line, a copper line, an optical line, a wirelesscommunication channel, an infrared communication link, or othercommunication path. A connection between two devices, such as device 405and device 410, is referred to as a link, such as link 415. FIG. 4illustrates a single lane in link 415; however, any number of lanes maybe present in a link such as 2, 4, 8, 12, 16, 32, 64, or wider.

A differential pair refers to two transmission paths, such as lines 416and 417, to transmit differential signals. As an example, when line 416toggles from a low voltage level to a high voltage level, i.e. a risingedge, line 417 drives from a high logic level to a low logic level, i.e.a falling edge. Differential signals potentially demonstrate betterelectrical characteristics, such as better signal integrity, i.e.cross-coupling, voltage overshoot/undershoot, ringing, etc. This allowsfor better timing window, which enables faster transmission frequencies.

Caching and Prefetching Hints

Referring to FIG. 5, an embodiment of a system capable oftransmitting/receiving caching/prefetching hints on a serialpoint-to-point link is illustrated. System memory 505 is coupled tocontroller hub 510 through memory interface 507. System memory 505includes any memory accessible by device 520 through controller hub 510,such as a RAM, NVRAM, or other know memory device. As stated above,controller hub 510 includes any controller, such as an MCH, ICH, orcombination thereof, which is commonly referred to as a chipset. Inanother embodiment, controller hub 510 is a root controller in a PCIehierarchy.

Device 520 is coupled to controller hub 510 through serialpoint-to-point link 515. I/O modules 511 and 521 include, i.e. arerepresented as, a protocol stack. In one embodiment, the protocol stackis a PCIe protocol stack and the serial point-to-point (SP2P) link is aSP2P PCIe link. In one embodiment, device 520 is an I/O device, such asa graphics accelerator, network interface controller (NIC), and anadd-in card.

Device 520 is to transmit a first packet, which is also referred to as arequest, message, transaction, or other known grouping of information,over SP2P link 515. In one embodiment, the first packet includes a cachehint and/or a prefetch hint. In one embodiment, caching hints, alsoreferred to as Access Control Hints (ACHs), potentially include temporalhints, locality hints, cache coherency hints, element usage intentionhints, or a combination thereof to influence caching policies associatedwith an element referenced by the first packet. According to oneimplementation, a prefetch hint includes any reference to an element tobe fetched for potential future use. An element includes any data,instruction, grouping of bits, cache line, or other known informationstored in a memory device.

Turning to FIG. 6, an embodiment of a non-exclusive list of devicerequest access semantics associated with cache and prefetch enhancementsis illustrated. Essentially, list 600 lists exemplary device requests toprovide temporal and/or locality caching/prefetching hints for efficientaccess and execution. In line 605 a base read is listed, and in line 635a base write is listed. In one embodiment, the base read is a normalbase read request with no caching or prefetching hints, and the basewrite is a normal base write request with no caching or prefetchinghints. In an alternative embodiment, a base read/write includes acaching hint.

In line 610 an intent to read and write indicates a device intends toread a cache line, or a plurality of cache lines, and subsequentlyintends to write to the cache line, or the plurality of cache lines.Here, caching hints and/or prefetching hints are included. Line 615listing a demand read and pre-fetch with intent to read indicates that adevice intends to read the demand portion of a cache line and intends tosubsequently read the same cache line or an additional cache line. Againa cache hint and/or a prefetch hint is/are included. Similarly, in line630 a demand write and prefetch with intent to write, indicates a devicewill write a demand portion of a cache line and intends to subsequentlyread the same cache line or an additional cache line.

Line 620 includes an intent to write back to memory, i.e. the devicerequests a cache line to be evicted from a cache and written back tomemory. Here, a cache hint and/or prefetch hint is/are included in therequest/message. Lines 635 and 640 include a direct I/O access, i.e. aread or write, which indicates a read but do not cache and/or awrite/direct cache access over a coherent fabric. Direct accesses arepotentially implemented utilizing Intel® Acceleration Technology (IOAT).More information regarding Intel® Acceleration Technology (IOAT) may befound at http://www.intel.com/technology/ioacceleration/index.htm.

In an embodiment, where prefetch hints messages are utilized, line 645,lists a prefetch message to carry prefetch information and accesscontrol hints (ACHs). As noted above, list 600 is an illustrative listof device accesses requests. Any device access request potentiallyincludes/references a caching and/or a prefetching hint.

Turning to FIG. 7, an embodiment of access control hints (ACHs)/cachinghints to be included in packet, request, and/or message is depicted. Inthe illustrated embodiment, five ACHs are listed: intent to read only,intent to read & write, intent to write only, evict, and direct I/O(DIO) access. Other potential hints include an intent to modify hint, anintent to writeback hint, a base read hint, a base write, and a basedefault hint.

Entry 705 indicates that the device intends to issue cache line readsonly. As a result, a cache, such as cache 512 from FIG. 5, may cache areferenced element. In one embodiment, a cacheline caching thereferenced element stores the element in an exclusive or shared state.Here, cache 512 is capable of storing cachelines in a cache coherencystate, such as a Modified, Exclusive, Shared, or Invalid (MESI) state.

Entry 710, i.e. intent to read and write ACH, indicates the device mayissue subsequent reads and writes to a cache line. Here, a referencedelement is fetched and held in an exclusive state, as it may bemodified. In contrast, entry 715, i.e. intent to write only, indicates adevice will potentially write to a cacheline. In this regard, areferenced cache line is held in an exclusive state, but a new elementassociated with the cache line is not fetched, as the line is intendedto be modified, not read.

Although any ACH may be a default ACH, entry 720 is depicted as thedefault ACH in this embodiment. Here, an evict ACH indicates the deviceis done, i.e. a referenced element/cache line may be evicted as thedevice does not intend to access the element/cache line in the nearfuture. Lastly, in entry 725 a direct I/O (DIO) ACH indicates that therequest is a direct I/O request, which is potentially associated withIOAT.

As indicated by the term hint, a cache or access control hint, providesan intention/hint with a request/message to potentially bias/influencecaching/eviction policy. However, cache control logic is potentiallycapable of ignoring an ACH, i.e. performing a cache/eviction operationinconsistent with the ACH. Furthermore, as list 700 is a non-exhaustivelist, any other bits/messages to influence caching/eviction policy maybe included as a first hint.

Referring to FIG. 8, an embodiment of a packet including a cache hint,i.e. an ACH, is illustrated. A packet refers to any request, message,access, or other grouping of information to be transmitted on abus/interconnect. In the embodiment shown, packet 800 includes otherinformation fields 805. Examples of other information 805 includesreserved fields, format fields, type fields, attribute fields, lengthfields, PCIe specific fields, and any other protocol specific fields. Inaddition, packet 800 includes requestor ID 815, which may reference arequesting agent/device and be part of a global ID/transactiondescriptor or include a global ID/transaction ID, as discussed above,and address field 820 to reference an address location.

ACH field 810 is a first portion of packet 800 to include a reference toan ACH, i.e. a caching hint. As illustrated, first portion 810 includesthree bits to specify an ACH; however, any number of bits may be used.Furthermore, first portion 810 may be located in any bit, byte, or otherposition of packet 800. As illustrated below, the ACH's listed in FIG.7, as represented by different predetermined bit patterns in field 810.For example, a bit pattern of 000 represents evict 850 ACH, while bitpattern 011 represents intent to read & write 865 ACH. First portionfield 810 may also be referred to as an opcode field, a message codefield, a type code field, or other code field.

In addition to temporal hints, locality cache hints may also beincluded. For example, a predetermined bit pattern in ACH field 810indicates that an element is to be cached in a root controller cache, adevice cache, system memory cache, or a processor cache.

In one embodiment, packet 800 is a read/write request packet, which maybe a message, a payload, and/or a header. Specifically, the read/writerequest packet/message/header is an enhanced/extended PCIE read/writerequest message/header. In this regard, ACH bits 810 may be presentanywhere in a read/write request header.

Referring next to FIG. 9 an embodiment of a prefetch packet/messageincluding a prefetch hint is illustrated. As in FIG. 8, packet 900includes other info 905, ACH field 910, requestor ID 915, tag field 920,message code 925 and address field 930. Here, in addition, prefetch hint940 is also included in packet 900. As stated above, a prefetch hintincludes any reference or hint to bias/influence fetching of additionalelements. In one embodiment, a prefetch is referred to as act of readingahead and maintaining coherent copies of prefetched cache lines.

In one embodiment, a prefetch hint includes any combination of prefetchparameters, such a count, a length, a stride, an offset, and adirection. In this example, a prefetch hint includes block count field941, length field 942, stride field 943, and direction field 944. Asillustrated, length field 941 is included in address field 930, whilethe rest of the fields are included in payload of the packet/message.However, fields 941-944 maybe included anywhere in prefetch message 900,including being distributed between a payload and a header or fullyincluded in one or the other.

As an illustrative example, block count field 941 includes five bits toreference a number of blocks between 0 and 31 to prefetch, block lengthfield 942 includes six bits to reference a number of cache lines between0 and 63 in a prefetch block, stride field 943 includes six bits toreference an offset, i.e. a number of cache lines between 0 and 63 untilthe start of a next block, and direction field 944 includes at least onebit to indicate and up or down direction to prefetch in.

A prefetch hint may include any other combination of fields/parametersto reference an additional element to be prefetched, such as a number ofblocks within a page or an interleave bit to indicate an order to fetchadditional cache line, i.e. elements, in. Furthermore, a prefetchmessage/hint may include some temporal use indication to indicate when adevice will issue a request for a block to influence/bias a rootcontroller cache's allocation and allocation policies.

As noted above, prefetch message 900 includes ACH field 910. Here, ACHfield 910 is to store an ACH associated with the additional elements,i.e. blocks/cache lines, to be prefetched. As above, a locality hintpotentially indicates where prefetched elements are to be cached and atemporal hint ACH indicates a device's access intention to bias cachingactions associated with the additional elements. Consequently, prefetchpacket 900, in one embodiment, includes a reference to an address, suchas a starting address or other address, a prefetch hint, and an accesscontrol hint (ACH).

Turning to FIG. 10 another embodiment of including a cache hint and aprefetch hint in a message/packet is illustrated. Here, packet 1000includes fields similar to packet 900, such as other information fields1005, ACH field 1010, requestor ID field 1015, tag 1020, message code1025, and address 1030. However, address field 1030 is a smaller size,while prefetch hint 1040, having parameter fields 1041-1044, is includedwithin byte 12 of a header. In one embodiment, packet 1000 is aread/write request header including a cache hint and a prefetch hint.

Referring back to FIG. 5, device 520, such as a graphics accelerator,includes I/O module 521 having a protocol stack to transmit a packetincluding a cache hint, i.e. an ACH, as described in reference to FIGS.6-10. In another embodiment, I/O module 521 is also to transmit a secondpacket, such as a prefetch message or read/write request, including aprefetch hint as described in FIGS. 6-10.

Controller hub 510, such as an MCH, is coupled to device 520 throughserial point-to-point interconnect 515. I/O module 511 is to receive thefirst and the second packet. In one embodiment, controller hub alsoincludes cache 512 to cache a first element in a MESI cache coherencystate based on an ACH in the first packet and additional elementsreferenced in the second prefetch packet. Controller hub 510 may alsoinclude fetch logic 513, which in one embodiment, is included in memoryinterface logic, to fetch/prefetch the additional elements, if an ACHindicates the additional elements are to be fetched. For example, if anACH represents an intent a modify only, no new data needs to be fetched,as the new data is to be modified anyway. In contrast, if the ACHrepresent an intent to read, then newer data is to be fetched to ensurethe proper data is read.

Consequently, cache 512 essentially is an elastic buffer tomanage/pipeline I/O traffic. Cache 512 may exhibit write cache, writethrough, and/or write-back attributes. However, cache 512 is not solimited, as it may be any style of known cache. Although notillustrated, in one embodiment bridges/switches in a PCIe hierarchy areable to pass through packets, requests, and/or messages, as well asroute caching/prefetching messages to a root controller.

In reference to FIG. 11, an embodiment of a flow diagram for a method ofproviding access control and/or prefetch hints is illustrated. In flow1105, a first packet including a reference to a first element and afirst hint is generated. The first packet is transmitted over a serialpoint-to-point (SP2P) link to a first device, such as a controller hubor root controller. In one embodiment, the SP2P link is a PCIE basedlink. The first device receives the first packet in flow 1110.

In flow 1115, a type of the first packet is determined. In a firstembodiment, the first packet is a read/write request message includingan ACH. The read/write request message may also include a prefetch hint.In another embodiment, the packet is a prefetch message including aprefetch hint. A packet type may be determined by an opcode field, amessage code field, or other field to specify a packet type. Inaddition, an ACH field and/or a prefetch hint field may be read todetermine the packet type.

If the packet includes an ACH and no prefetch hint, then in flow 1120the first element is fetched, if the ACH indicates the first element isto be fetched. In flow 1125, the first element, such as a cache line, isstored in a first MESI cache coherency state based on the first ACH.

If the message is a read/write request with an ACH and a prefetch hint,then after flows 1120 and 1125, the flow moves to block 1130. However,in one embodiment where the message is a prefetch message, then the flowmay go directly to flow 1130 without passing through blocks 1120 and1125.

In flow 1130, an additional element, or a plurality of additionalelements to be prefetched is determined based on a prefetch hint. Theprefetch hint includes any combination of prefetch parameters, such as astarting address, a block count, a length, a an offset, a stride, and adirection. In flow 1135, the additional element is prefetched. As above,the additional element is stored in a cache coherency state based on anACH associated with the prefetch message.

Atomic Operations and Synchronization Primitives

Referring to FIG. 12, an embodiment of a system capable of performingatomic operations is illustrated. System 1200 allows efficient exchangeof status information and semaphores through fast “ownership” exchangeof data shared between multiple devices. Previously, an I/O device wouldacquire a system wide lock on a shared location in memory, performoperations on the shared location, and then release the lock. However,device 1220 is capable of requesting an atomic operation. In oneembodiment, an atomic operation includes a read, modify, and write (RMW)to a shared memory location. In another embodiment, an atomic operationincludes a read request. As an illustrative example, an atomic operationis to operate on 4B, 8B, and 16B aligned data.

As another illustrative example, RMW engine 1222 is to request/specifyan atomic operation, i.e. a RMW to meta-data/semaphore 1206, to acquireownership of data unit 1207. Data unit 1207 includes any granularity oflockable data, from a single bit, a single element, a single cache line,a block of elements/cache lines, a table, or any othergranularity/grouping of data. In one embodiment, RMW engine 1222 is alsoto track the atomic operation, which it is outstanding. Interface 1221,which includes a layered protocol stack, is to transmit a packet/messagespecifying the atomic operation to controller hub 1210. Detection/decodelogic 1212 in interface 1211 is to detect the atomic operation, such asthrough a predetermined bit pattern. Service logic 1213 services theatomic operation, i.e. RMW to location 1206. In response to completingthe RMW, logic in controller hub 120 generates a response message to betransmitted over SP2P link 1215 and received by device 1220. In thisregard, RMW engine retires the tracking of the outstanding atomicoperation.

In one embodiment, semaphore 1206 is a shared data structure, to acquireownership of data unit 1207. As a result, two threads, such as threads1226 and 1227 executing on processor 1225, share access to semaphore1206, and accordingly data unit 1207, such as a hash table or othergranularity of data, with device 1220. As a result, instead of acquiringa system wide lock with device 1220, which stalls thread 1226 and 1227from concurrently operating on data in data unit 1207, and atomic updateof semaphore is serviced by controller hub 120. In other words, device1220 is essentially treated as a co-equal thread/processor able toperform atomic operations on shared data locations. Therefore, a writeto meta-data/semaphore 1206 and an exchange of the value in location1206 is atomically completed, if a right value exists in semaphorelocation 1206.

Turning to FIG. 13, an embodiment of a packet/request/message to specifyan atomic operation is illustrated. Packet 1300 includes any message orrequest, such as a read/write PCIe request. As above in reference toFIGS. 8-10, any fields may be included in packet 1300, such as otherinformation 1305, ID 1310, tag 1315, and address fields 1330. As above,ID 1310 potentially includes a transaction descriptor, a portion of atransaction descriptor, a unique transaction ID, a global ID, an agentID, a local ID, or combination thereof. As IDs are utilized to trackoutstanding atomic operation, as discussed below, a device, such asdevice 1220 may generate multiple outstanding atomic operations.

Also included in packet 1300 is message code 1320. Message code 1320 isto specify an atomic operation. In one embodiment, message code 1320 isan opcode to be recognized/detected by detection logic, such asdetection logic 1212. Alternatively, an opcode field is included inpacket 1300, such as in other info field 1305, to identify a request ormessage, such as a read/write request. In this example, message code1320 is potentially a separate field to be detected/decoded bydetection/decode logic 1212. Message code 1320 may also be referred toas a type field or other known predetermined bit field.

In one embodiment, second portion 335 of message code 1320 specifies aninstruction and first portion 330 indicates if the instruction isatomic. An illustrative example of the second portion being appended tothe first portion is depicted in FIG. 13. Here, Atomic identifier (AID)field 330 indicates an instruction referenced in instruction field 335is atomic, if bits in field 330 include a predetermined bit pattern of011. In AID field 330 includes any other bit pattern, then theassociated instruction is determined to not be atomic. Instruction field335 identifies an instruction, such as BitSet instruction 321, BitClearinstruction 322, Two's complement Add instruction 323, add instruction324, swap instruction 325, and test and swap instruction 326.

In an embodiment where an atomic operation includes RMW operations, anyinstruction capable of RMW may be used as an atomic instruction. Incontrast, in an embodiment where atomic operations include reads, anyread instruction may be utilized. As a result, FIG. 13 depicts anillustrative non-exhaustive list of potential atomic operations, whichmay be modified. In another embodiment, packet 1300 includes vendor IDfield, which is potentially used to ID a vendor or allow for a vendorspecified identification.

Referring quickly back to FIG. 12, RMW engine 1222 requests/specifies anatomic operation. An ID, such as a global ID, transaction ID, or otherunique ID is used to track outstanding atomic transactions. For example,an entry in a data structure, such as a queue, stack, or linked list,tracks a status of an atomic transaction. In one embodiment, RMW engine1222 allocates space in a device, such as in local memory and/or thedata structure, for an atomic transaction response before issuing anatomic transaction. Once an atomic transaction is serviced, i.e.completed, a response message is generated and received by the initialrequesting device, i.e. device 1220. The response message is to includea unique ID, which may be used both to route the message back to device1220 and to locate/retire an outstanding atomic transaction in the datastructure.

Turning over to FIG. 14, an embodiment of a response message isillustrated. As above, response message 1400 may include otherinformation 1405, such as other information in a PCIE response message.In addition, response message 1400 is depicted as including completer ID1410 to identify a completing agent, byte count 1415 to reference a bytecount, requestor ID 1420, tag 1425, and lower address 1430. A unique IDassociated with the atomic transaction is included in response 1400. Asan example, the unique ID is includes a combination of the depicted IDsor is within a depicted ID field. However, a unique ID may be locatedanywhere in response 1400. As another example, a portion of atransaction descriptor, a transaction descriptor, a global ID, a localID, or other ID, as described above, is included in response 1400.

In one embodiment, response 1400 is generated in response to servicingan atomic operation. In this regard, an initial or old value is returnedwith response message 1400. As an example, an atomic operation isspecified in a read write request generated by a graphics accelerator.The atomic operation is to perform a RMW on a first memory location. Theread/write request is received by a controller hub including a layeredprotocol stack. The first memory location is read to return a value of0, the value of 0 is modified to a 1, and the 1 is written to the firstmemory location. Response message 1400 includes a unique atomictransaction ID and old/initial value 0. When the response message 1400is received by the graphics accelerator, it is retired from a datastructure tracking the atomic transaction as outstanding throughreference to the unique atomic transaction ID.

In one embodiment, service logic, such as service logic 1213 includesany logic to service an atomic transaction. For example, service logicincludes logic to perform a read of a first value from a memorylocation, a modify of the first value to a second value, and a write ofthe second value back to the first memory location. An RMW may also bereferred to as an exchange, a compare and exchange, and a test andexchange.

Referring next to FIG. 15 an embodiment of a flow diagram for performingan atomic operation is illustrated. In flow 1505, a first packet isgenerated with a device. The first packet is to include a reference tothe first atomic operation and a unique transaction ID. In oneembodiment the device includes a graphics accelerator. Furthermore, thereference to the first atomic operation includes a reference to anatomic instruction, such as BitSet, BitClear, Two's Complement Add, Add,Swap, and Test & Swap.

In another embodiment, the device stores a reference to the uniquetransaction ID for tracking purposes. Moreover, as an example, space isallocated for a response message to the first packet before issuing thefirst packet. The first packet is then transmitted using a layeredprotocol stack to a controller hub over a SP2P link. Note that the firstpacket may be transmitted over a plurality of SP2P links and routedthrough bridges/switches to reach a controller hub, such as a rootcontroller hub.

The first packet is received with the controller hub through a layeredprotocols stack in flow 1510. The controller hub detects the referenceto the atomic operation. In one embodiment, a predetermined bit patternspecifies the atomic operation from the atomic operations mentionedabove. In flow 1515, the atomic operation is serviced. In an embodiment,where an atomic operation includes an atomic RMW, the RMW is performedatomically.

Next, in flow 1520 a response message is generated in response toservicing the atomic operation. Here, the response message is to includean old value and a reference to the unique transaction ID. In oneembodiment, the old value is a value read while servicing the atomictransaction. The response message is transmitted back to the device. Inregards to this, a unique transaction ID, which references an originalrequestor, i.e. the device, is potentially used to route the responsemessage back to the correct device.

In flow 1525 the response message is received by the device, and in flow1530 the reference to the atomic operation is retired based on theunique transaction ID. Essentially, the reference to the unique IDstored in the device for tracking purposes is retired, as the responsemessage indicates the atomic operation associated with the unique ID hasbeen serviced.

Loose Ordering

Referring to FIG. 16, an embodiment of re-ordering transactions isillustrated. System memory 1605 is often logically broken up andaccessible in pages to more efficiently manage/access memory. As aresult, system memory 1605 is illustrated as broken into pages1606-1608. Page 1606 includes memory locations B and D, page 1607includes memory location A, and page 1608 includes memory locations Cand E.

Device 1620 generates a first number of transactions. Transactions 1616are transmitted through a protocol stack in interface 1621 on SP2Pinterconnect 1615. I/O module 1611 in controller hub 1610 receivestransactions 1616 in a first order. As illustrated, the secondtransaction in the first order references memory location B in page1606, as denoted by B₀, while the eighth and the last transaction in thefirst order also references location B, as denoted by B₁. Othertransactions in the first order are represented similarly.

Controller hub 1610 also includes re-order logic 1612 to re-ordertransactions 1616 to second order 1617. In one embodiment, re-orderlogic 1612 is included in a core of controller hub 1610. However,reorder logic 1612 may be included anywhere in controller hub 1610,including I/O module 1611. Furthermore, transactions 1616 maybere-ordered from an original order in protocol stack 1621, oninterconnect 1615, and/or by logic in protocol stack 1611.

Re-order logic 1612 is to order first number of transactions 1616 tosecond order 1617, which is different than the first order, based atleast in part on maintaining priority of a plurality of correspondingtransactions. In one embodiment, corresponding transactions includetransactions that refer to the same memory location, such as a firsttransaction and a second transaction that reference a first memorylocation. In this regard, transactions A₀/A₁ and B₀/B₁ are correspondingtransactions, as they reference the same memory location. Other factorsmay be used to determine corresponding transactions, such as sequentialordering or other addressing techniques.

In one embodiment, maintaining priority includes not allowing a firsttransaction of a plurality of corresponding transactions to be orderedafter a second transaction of the plurality of correspondingtransactions in the second order, where the first transaction precedesthe second transaction in the first order. In other words, not allowinga plurality of corresponding transactions to pass each other. Or, notordering a first transaction, which preceded a second transaction in thefirst order, subsequent to the second transaction in the second order

For example, transaction B₀ is issued before, i.e. preceding, B₁, in thefirst order. In second order 1617 B₁ is not allowed to pass B₀, asdemonstrated by B₀ being placed before B₁ in the second order. From arelative perspective of the memory location, such as memory location B,B₁ cannot be ordered to access location B before B₀ does. Logically, ifB₁ is a write to a location B that is to occur after B₀ reads fromlocation B, if B₁ is serviced first, then inaccurate data would be readby servicing B₀ second.

However, in one embodiment any other combination of factors, such asefficient access to pages, access pattern, sequential addressing, andservice time are used to determine the second order. For example, if thefirst order is executed verbatim, page 1607 is opened to servicetransaction A₀, page 1607 is then closed, page 1606 is opened to servicetransaction B₀, page 1606 is then closed, page 1608 is then opened toservice transaction C, page 1608 is closed, and page 1606 is reopened toservice transaction D. This inefficient page access may be referred toas thrashing, when accesses alternate between pages.

As a result, second order 1617 accounts for efficient page access inthat, page 1606 is opened to service transactions B₀, B₁, and D, page1606 is closed and page 1607 is opened to service transactions A₀ andA₁, and then page 1607 is closed and page 1608 is opened to servicetransactions E and C. Here, pages are efficiently accessed to save onaccess/service time. Service logic to perform/service the transactionsmay also be included in controller hub 1610.

FIG. 17 depicts an embodiment of a method for loosely orderingtransactions. In flow 1705, a first number of transactions are receivedon a serial point-to-point link, such as a PCIE link. In flow 1710, asecond order of the plurality of transactions is determined. In oneembodiment, the second order is to be based at least in part onmaintaining a priority of a plurality transactions of the first numberof transactions. The plurality of transactions corresponding, i.e. eachof them reference a first memory location.

In one embodiment, maintaining a priority of the plurality oftransactions includes not allowing a first transaction of the pluralityof transactions to be ordered after a second transaction of theplurality of transactions in the second order. Here, the firsttransaction precedes the second transaction in the first order, so thesecond transaction is not allowed to pass the first transaction in thesecond order. In one embodiment, the second order is different from thefirst order the first number of transactions is received in.Furthermore, in another embodiment, the second order is also based atleast in part on an additional parameter selected from a groupconsisting of an access pattern, sequential addressing, and a servicetime, i.e. how long it will take to service the transaction from anestimate or past access. Next in flow, 1715 the transactions areserviced in the second order, i.e. the transactions are performed.

Performance/Power Active Sub-States

Turning to FIG. 18, an embodiment of active power sub-states associatedwith performance and power metrics in a device is illustrated. In oneembodiment, table 1815 stores power states associated with performanceand power metrics. In one embodiment, table 1815 is made up of aplurality of storage elements in a device. For example, 12 configurationregisters in a device store entries 1850-1861.

In one embodiment, the power states are active power sub-states. Here,in each active sub-state, a device is able to perform I/O tasks;however, each active sub-state is associated with different power andperformance metrics to consume different levels of power or operate atdifferent levels of performance. In contrast, non-active power statesare potentially associated with different power consumption levels;however, the non-active power states typically included different levelsof “off”, where an I/O device is not able to perform I/O operations orother primary functions.

In the example illustrated, table 1815 includes four active powersub-states, i.e. sub-states 1-4. However, any number of sub-states, suchas seven, may be associated with performance and power metrics in table1815. As an example, sub-state 1, in entry 1850, is associated with atransition latency less than 1 us in column 1825, a performance ratio of15/16 in column 1830, a voltage of 12V in column 1835, and a power of 25W in column 1840. Note that there are three entries per activepower-sub-state in FIG. 18, such as entries 1850-1852 for sub-state 1.Here, a voltage value of 12V and 3.3V represents a maximum voltage valuefor two voltage rails of 12V and 3.3V in column 1835, while a thermalvalue, is represented in entry 1852. In another embodiment, a fourthentry per sub-state includes a third voltage value for a third voltagerail. As an example, a third max voltage for a third rail is 1.8V.

The transition latencies listed in column 1825 may represent any latencyassociated with a power state. Examples of transition latencies includea transition latency into an active sub-state from a maximum powerstate, a transition latency out of the active sub-state to another powerstate, a transition into the active sub-state from a previous activesub-state, and a transition out of the active sub-state into a nextactive sub-state. Also note, that these values may be relative orabsolute.

For example, a transition latency of less than 5 us for active sub-statethree in entries 1856-1858, in one embodiment, represents an absolutetransition latency. In this regard, column 1825's fields represent atransition latency out of active sub-state 3 to a maximum activesub-state, such as sub-state 1, or a minimum sub-state, such as 4, atransition latency into the maximum or minimum sub-state fromactive-substate 3, or a combination thereof. Alternatively, asillustrated, fields in column 1825 represent relative transitionlatencies. For example, less than 5 us in entries 1856-1858 represent atransition latency of less than 5 us for transition out of activesub-state 3 into active sub-state 2, for transition into activesub-state 2 out of active sub-state 3, or a combination thereof.

In this later example, when in sub-state 1, values in fields 1825 areadded to determine a transition latency for transitioning into a loweractive power sub-state. To illustrate, a transition from sub-state 1 tosub-state 4 includes a latency of <1 us+<5 us+<10 ms. In contrast, table1815 may be constructed to represent transition latencies from a minimumactive power sub-state, such as 4, up to a maximum power sub-state of 1.Here, entries 1859-1861 include smaller transition latencies from aminimum low power state then entries 1850-1852, which would includehigher transition latencies.

It is also worth noting, that some data fields, such as fields incolumns 1820, 1825, and 1830 are repeated within the three entries foran active sub-state. In one embodiment, these values are different. Inanother embodiment, table 1815 is stored as a 2-dimensional word arrayor other data structure to minimize repeated fields between activesub-state entries.

As stated above, table 1815, which may be represented as any datastructure, such as a list, an array, a 2-d array, a multi-dimensionalarray, or other known data structure, is to associate a performancemetric and potentially a power metric with an active power sub-state.Examples of a power metric include: a maximum voltage value, a minimumvoltage value, an absolute voltage value, a maximum power consumptionvalue, a minimum power consumption value, and an absolute powerconsumption value, and a vendor defined power metric. Examples of aperformance metric include a sub-state performance value, an operationalfrequency value, a sub-state operational unit value, a sub-state thermalvalue, a sub-state transition latency value, a fractional value ofmaximum performance, a number of sub-units to be active, a fractionalnumber of pipelines to be active, a thermal value, a voltage, a vendordefined performance value, and a device defined performance value.

Although listed separately, power and performance metrics are not alwaysmutually exclusive. For example, if a graphics accelerator has fourpipelines/sub-units, a performance value to indicate how many of thefour pipelines/sub-units are to be activated also affects powerconsumption, as the power consumption for 1 active pipeline is likelyless than the power consumption of 4 active pipelines. Note a sub-unitmay include any function unit of a device, such a pipelines, queues,logical blocks, functional blocks, or other potential sub-units.

Also illustrated in FIG. 18 is second storage element 1805. In oneembodiment, second storage element 1805, as well as entries 1850-61, areconfiguration registers in a configuration space of a device. Storageelement 1805 is to receive a write to set/request/select an active powersub-state. In another embodiment, register 1805 is also potentiallywritten to set an inactive power state.

Typically a write is received from an external agent or software.However, in one embodiment, a device is able to write to its ownregister 1805 to set a power state. Often devices setting power statesis not advantageous, as they typically do not have a view of systempower consumption. However, in one example, when a maximum active powerstate is requested/set, a device may set a lower active power state, aslong as a transition latency or other performance/power metrics do notaffect performance drastically. For example, if a requested sub-state of1 is written to field 1806, a device, in this example, may selectsub-state 2 in field 1807, as it consumes less power/thermal budget thanmaximum active sub-state 1. However, a device may not be able to selectactive sub-state four in field 1807, as a transition latency of <10 msand/or a performance ratio of 1/16 is deemed too low. In anotherembodiment, a device is able to set any active power sub-state.

However, more typically, when an interrupt field, such as field 1809 isset, interrupt requests from the device are enabled to request a changeto the active sub-state. Here, a device generates an interrupt torequest an active sub-state change. Firmware or another external agenttraps the interrupt and writes back to register 1805 to set therequested active sub-state. In one embodiment, the write back toregister 1805 is to set field 1806 to the requested sub-state. Inanother embodiment, the device writes the requested sub-state in field1806 and the write-back is to set sub-state select field 1807.

Therefore, in response to setting the sub-state request field 1806and/or sub-state select field 1807, the device is then set to theselected active power sub-state by setting the power and performancemetrics associated with the selected sub-state in field 1807. Forexample, if sub state select 1807 is set to active sub-state 2, then themetrics in entries 1853-55 associated with sub-state 2, such aperformance ratio of 12/16, are set. As above, latency 1808 may includeany transition latency, including a latency to transition in and/or outof a requested sub-state to/from a selected sub-state. In addition tablesize field 1810 may include a number of entries, a number of fields, orother size measure of table 1815.

Although not illustrated, a system power management module, which mayinclude power management software, a power management controller, orother logic, firmware, or software in a system is to set a powerconsumption limit for a device. In one embodiment, the power consumptionlimit is based at least in part on any combination of factors, such as atotal amount of power available to a system, a total amount of heatcapable of being dissipated by the system, an amount of current powerconsumption of the device, an amount of heat currently generated by thedevice, a current active state of the device, a workload of the device,an interrupt request from the device to change to an active sub-state, acurrent operating frequency of the device, and a number of sub-units inthe device that are active.

In this regard the system power management module is to comprehendsystem wide power and performance issues. For example, a system powermanagement module (SPMM) is able to measure or read an amount of powerable to be generated for the system by a power supply. Based on thetotal power, workloads of devices, such as processors and I/O devices,and requested power states of the devices, the system power managementmodule sets power/performance consumption limits for each device. If arequest for a power state above a set limit for a device is requested,the power state change request is potentially denied. An SPMM may alsocomprehend other system factors, such as a total amount of heat capableof being dissipated in a system. As a result, the SPMM is to write tostorage element 1805, the write referencing an active sub-state, whichis based on the power consumption and/or thermal limit for the deviceand/or a system the device is included within.

Referring next to FIG. 19 an embodiment of a flow diagram for a methodof setting an active sub-state in a device is illustrated. In flow 1905,an interrupt is generated with an I/O device to request a change to anactive power sub-state. As noted above, the interrupt may be trapped byfirmware or other agent. A write to the I/O device is generated to setthe active power sub-state in response to servicing the interrupt.Before generating an interrupt, an interrupt field in a first storageelement may be set to enable generation of interrupts.

In flow 1910 a write to a first storage element is received through alayered protocol stack in the I/O device. In one embodiment, the firststorage element is a configuration register in a configuration registerspace of the I/O device. The write is to set a field in the firststorage element to the active sub-state or another active-sub statebased on the request. In one embodiment, the I/O device is a PCIE deviceincluding a PCIE layered protocol stack. Next, in flow 1915 therequested active power-sub state is stored in the first storage element.

A metric associate with the active-power sub-state is determined from asecond storage element. In one embodiment, the second storage element isa configuration register in a configuration register space of the I/Odevice. As a first example, the active sub-state is located in adata-structure including the second storage element, and a metricassociated with the active sub-state in the second storage element isread out.

In one embodiment the metric is a performance metric, as describedabove. In another embodiment, the metric is a power metric, as describedabove. Examples of a metric include a frequency, a latency, a transitionlatency, a thermal value, a number of sub-units of the I/O device to beactive, a performance percentage of a maximum performance, a vendordefined performance metric, a voltage, a rail voltage, a power value,and a percentage power value of a maximum power. Next, in flow 1925, themetric is configured in the I/O device in response to string therequested active power sub-state in the first storage element.Essentially the power and performance metrics are set to the activepower sub-state values to set the I/O device to the active powersub-state.

Device and Shared Memory Window Caching

In FIG. 20, an embodiment of a system capable of mapping portions oflocal and system memory into each other as caches is illustrated. Heresystem memory 2005 includes any shared memory, such as a DRAM, NVRAM, orother memory device. System memory 2005 is typically available inshared/host memory space 2009, although some portions may be invisibleto host memory space 2009.

Here, device 2020 is associated with local memory 2022, which mayinclude SRAM, NVRAM, or other local memory. Device 2020 includes an I/Odevice, such as a graphics accelerator, add-in card, network processor,or other I/O device. Portion 2023 of local memory 2022 is mapped intohost address space 2009. As a result, a processor, not shown, or otherdevice is able to see mapped local memory window 2008 as part of hostaddress space 2009. As a result, other resources are able to shareaccess to device 2020's local memory 2022 through window 2008.

In one embodiment, Base Address Register (BAR) 2025 to store a baseaddress for device 2020 is utilized to map portion 2023 into host memoryspace 2009. Often in a page table structure, a BAR stores a startingaddress for a logical/linear/virtual view of memory. For example, a BARincludes a reference to a page director entry (PDE), that stores areference to a page table entry (PTE), that includes a range ofaddresses/offsets. In this regard, the BAR stores a reference to anaddress within host address space 2009 to include window 2008. Note thatsome portions of local memory 2022 are potentially invisible in systemmemory space 2009.

In one embodiment, mapped local memory window 2008 is to be utilized asa cache for local memory 2022 to improve bandwidth and latency foraccesses to local memory 2022 by another device, such as a processor insystem 2000. As a result, elements are fetched to window 2008 from localmemory 2022 and potentially stored in cache coherency states, such asMESI states. Other devices, such as processors in system 2000 accesslocal memory 2022 through window cache 2008. When an element isrequested and a hit in window 2008 occurs, the element may be directlyprovided to a requesting agent. In contrast, upon a miss the requestedelement is fetched from local memory 2022.

In one embodiment, window cache 2008 is utilized as a write-back cache,where elements are stored in window 2008 and later written-back to localmemory 2022. Other styles/attribute of caches, such as write-throughcaches, may also be used. In another embodiment, snoop filter 2012 isincluded in controller hub 2010 to filter snoops to/from window cache2008 to reduce snoop traffic on memory interface 2016 and on SP2P link2015.

Similar to mapping of a portion of local memory 2022, in one embodiment,portion 2006 of system memory 2005 is mapped into local memory 2022 tobe utilized as an accelerator cache of system memory. Here, operation issimilar to window I/O cache, as mapped system memory portion 2023operates as window cache 2023. In one embodiment, window cache 2023utilizes write-back cache memory attributes to interface through SP2Plink 2015 and memory interface 2016 with system memory 2005. In oneembodiment, mapping of system memory portion 2006 into local memory 2023includes setting a portion of system memory 2006 as logically viewablein device 2020's local memory address space.

In one embodiment, snoop filter 2024 is to filter a first plurality ofsnoop requests associated with the local memory. In other words, snoopfilter 2024 is to track a first number of lines of local memory 2022that are cached in window cache 2008 and to filter snoops to a secondnumber of lines of local memory 2022 that are not cached. Similarly,snoop filter 2012 is to track a first number of lines of system memory2025 that are cached in window cache 2023 and to filter snoops to asecond number of lines of system memory 2005 that are not cached.

FIG. 21 illustrates an embodiment of a system including an I/O devicehaving a cache. System 2100 includes any electronic system, such as acomputer system. Processor 2125 is coupled to controller hub 2110through front-side bus (FSB) 2126. Controller hub 2110 is coupled tosystem memory 2105 through memory interface 2109 and to I/O device 2120through SP2P link 2115. I/O modules 2111 and 2121 implement a layeredprotocol stack to facilitate communication between device 2120 andcontroller hub 2110. In one embodiment, controller hub 2110 includes acache. For example, controller hub 2110 is a chipset including a chipsetcache. In one embodiment, snoop filter 2112 is present and/or replicatedin device 2120.

With cache 2122 residing in device 2120, potentially newrequests/transactions are available to support I/O device caching. Forexample, new possible upstream requests include a read share for cache2122 to mark a line shared, a read current to get a snapshot, a readexclusive to mark a line in exclusive or modified state on a write. Inaddition, a downstream snoop invalidate transaction is supported forshared or exclusive/modified states. Moreover, new responses may besupported such as a writeback response with/without data thatrelinquishes ownership, a snoop response with/without data thatrelinquishes ownership, and a data response for any MESI state.

In one embodiment cache 2122 exhibits write-back and/or write-throughcaching attributes. In this regard, cache 2122 and cache 2112 operate tocache system memory 2105 elements in different locations in system 2100.Consequently, locality caching hints, as discussed above, may beutilized to cache specific lines/elements in different location toenable quicker access. As a result, control logic in cache 2122 may alsobe capable of receiving and interpreting prefetch/caching hints.

In addition, an I/O device cache, such as cache 2122 is capable ofcaching lines in cache coherency states in addition to traditional MESIstates. As a first example, cache 2122 holds a line in a Fetch InProgress (FIP) state indicating a fetch is in progress. Another exampleincludes a Snapshot (C) coherency state to indicate a snapshot of acache line.

Examples of Device 2120 include a graphics accelerator, a networkcontroller, an add-in card, an audio processor, or other I/O device. I/Odevice 2120 includes cache 2122 capable of maintaining cache lines in aMESI cache coherence state. A root controller, such as controller hub2110, in one embodiment, maintains a directory of cache lines cached bydevice 2120. In this regard, snoop filter 2112 stores a page address, astatus indicator, a host physical address for the page, and a requestingID of the requesting agent that is caching a referenced line. As aresult, snoop filter 2112 may be partitioned among multiple I/Odevices/switches.

As illustrated above, temporal and locality caching/prefetching hintsare capable of being provided in a SP2P interconnect fabric.Specifically, in PCIe requests/messages hints are provided to enablemore efficient memory access, caching, and prefetching for subsequentexecution. In addition, extensions/enhancements including new messagecodes allow for atomic operations to be performed/requested by PCIedevices. As a result, the expensive locks by I/O devices to sharedmemory locations may be avoided, and thereby arbitrated among allresources to provide efficient atomic ownership acquisition of shareddata locations.

Furthermore, transactions are able to be re-ordered to provide forefficient page table memory accesses while ensuring memory locationintegrity by maintaining priority of corresponding transactions to asame memory location. As previous PCIe essentially included one activepower state and a plurality of inactive power states, new configurationregisters and system power management techniques allow for moreefficient power and performance management. Finally, mapping of devicelocal memory as a window cache in a host memory space, and inversely,system memory as a second window cache in the device local memory spaceenables efficient latency and bandwidth access between processors andPCIe devices.

The embodiments of methods, software, firmware or code set forth abovemay be implemented via instructions or code stored on amachine-accessible or machine readable medium which are executable by aprocessing element. A machine-accessible/readable medium includes anymechanism that provides (i.e., stores and/or transmits) information in aform readable by a machine, such as a computer or electronic system. Forexample, a machine-accessible medium includes random-access memory(RAM), such as static RAM (SRAM) or dynamic RAM (DRAM); ROM; magnetic oroptical storage medium; flash memory devices; electrical, optical,acoustical or other form of propagated signals (e.g., carrier waves,infrared signals, digital signals); etc.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

In the foregoing specification, a detailed description has been givenwith reference to specific exemplary embodiments. It will, however, beevident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the invention asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense. Furthermore, the foregoing use of embodiment andother exemplarily language does not necessarily refer to the sameembodiment or the same example, but may refer to different and distinctembodiments, as well as potentially the same embodiment.

What is claimed is:
 1. An apparatus comprising: a receiver to receive atransaction layer packet from an input/output (I/O) device, wherein theI/O device comprises an add-in card, the transaction layer packet is tocomprise a header, and the header is to comprise: a first byte of theheader, a second byte adjacent to the first byte, wherein the secondbyte is to include a hint field, and the hint field is to identify ahint in the transaction layer packet; and a no-snoop attribute to beincluded in another byte of the header subsequent to the first byte; andprotocol circuitry to process the transaction layer packet.
 2. Theapparatus of claim 1, wherein the protocol circuitry is to identify thehint from the hint field, and the apparatus further comprises coherencylogic to determine whether to snoop a transaction based on the no-snoopattribute.
 3. The apparatus of claim 2, wherein the coherency logic isto provide cache coherency management and cache coherency management isto include snoop requests of one or more shared memory locations.
 4. Theapparatus of claim 3, wherein cache coherency management is to furtherinclude filtering of the snoop requests.
 5. The apparatus of claim 4,wherein the one or more shared memory locations include a first sharedmemory location and a second shared memory location, the transactionincludes a request on the first shared memory location, the transactionlayer packet is to include a cache coherency attribute, and the cachecoherency attribute is to indicate that snoop requests corresponding tothe request are to be filtered.
 6. The apparatus of claim 5, whereinsnoop requests of the second shared memory location are not filtered. 7.The apparatus of claim 5, wherein the cache coherency attribute isincluded in an attribute field of a transaction layer header of thepacket.
 8. The apparatus of claim 1, wherein the transaction layerpacket is to correspond to a transaction.
 9. The apparatus of claim 8,wherein the transaction is to comprise a request on shared memory. 10.The apparatus of claim 9, wherein the shared memory is to comprise acache.
 11. The apparatus of claim 10, wherein the shared memory is tocomprise a system cache.
 12. The apparatus of claim 10, wherein theshared memory is to comprise a local cache of a device.
 13. Theapparatus of claim 1, wherein the transaction is to comprise an atomicoperation.
 14. The apparatus of claim 1, wherein the receiver andprotocol circuitry are included in a root controller of the apparatus.15. An apparatus comprising: a receiver to receive a transaction layerpacket over a point-to-point interconnect, wherein the transaction layerpacket is to correspond to a transaction and is to comprise a header,the header is to comprise a first byte of the header, a hint field is tobe included in a second byte of the header adjacent to the first byte,and a transaction descriptor in another byte of the header subsequent tothe second byte, the transaction descriptor is to comprise a no-snoopattribute, and the hint field is to identify a hint in the transactionlayer packet; a layered protocol stack to comprise a transaction layer,a link layer, and a physical layer, wherein the layered protocol stackis implemented at least in part by protocol circuitry to identify a hintfrom the hint field; and coherency logic to identify, from the no-snoopattribute, whether snoop filtering applies to corresponding snooprequests of shared memory associated with the transaction.
 16. Anapparatus comprising: an interface to: interface with an add-in card;and send a transaction layer packet to the add-in card, wherein thetransaction layer packet is to correspond to a transaction and is tocomprise a header, the header is to comprise: a first byte of theheader, a second byte of the header adjacent to the first byte, whereinthe second byte is to include a hint field, and the hint field is toidentify a hint in the transaction layer packet, and a transactiondescriptor in another byte of the header subsequent to the second byte,wherein the transaction descriptor is to comprise a no-snoop attributeand the hint field is to identify a hint in the transaction layerpacket.
 17. An apparatus comprising: protocol logic implemented at leastin part in computing hardware, wherein the protocol logic is to: receivea transaction layer packet from an input/output (I/O) device, thetransaction layer packet is to comprise a header, and the header is tocomprise: a first byte of the header, a second byte of the headeradjacent to the first byte, wherein the second byte is to include a hintfield to identify a hint in the transaction layer packet, and a no-snoopattribute to be included in another byte of the header subsequent to thefirst byte; and process the transaction layer packet based at least inpart on the hint and the no-snoop attribute.
 18. The apparatus of claim17, wherein at least a portion of the protocol logic is implemented insoftware.
 19. A method comprising: receiving a transaction layer packetover a point-to-point interconnect, wherein the transaction layer packetis to correspond to a transaction and is to comprise a header, theheader is to comprise a first byte of the header, a second byte of theheader adjacent to the first byte, and a transaction descriptor inanother byte of the header subsequent to the second byte, wherein thesecond byte is to include a hint field to identify a hint in thetransaction layer packet, the transaction descriptor is to comprise ano-snoop attribute, and the hint field is to identify a hint in thetransaction layer packet; identifying a hint from the hint field; anddetermining whether to snoop a transaction based on the no-snoopattribute.
 20. The method of claim 19, further comprising filteringsnoop requests based at least in part on the no-snoop attribute.
 21. Themethod of claim 20, wherein the transaction comprises a request onshared memory.
 22. A system: a first device; and a second devicecomprising I/O circuitry to: receive a transaction layer packet from thefirst device over a point-to-point serial data link, wherein thetransaction layer packet is to correspond to a transaction associatedwith shared memory; identify a hint field in a header of the transactionlayer packet, wherein the header is to comprise a first byte and asecond byte of the header adjacent to the first byte, and the hint fieldis to be included in the second byte; identify a no-snoop attribute inthe header, wherein the no-snoop attribute is to be included in anotherbyte of the header subsequent to the second byte.
 23. The system ofclaim 22, wherein the second device comprises a root controller hub. 24.The system of claim 22, wherein the first device comprises an add-incard.
 25. The system of claim 24, wherein the system comprises means toaccept the add-in card.
 26. An apparatus comprising: a connector toaccept a card device, wherein the connector comprises logic to: receivea transaction layer packet from the card device, the transaction layerpacket is to comprise a header, and the header is to comprise: a firstbyte of the header, a second byte adjacent to the first byte, whereinthe second byte is to include a hint field, and the hint field is toidentify a hint in the transaction layer packet; and a no-snoopattribute to be included in another byte of the header subsequent to thefirst byte.
 27. The apparatus of claim 26, wherein the connector is tobe included in a server system.